RavensPort, published by Abishek Narasimhan and currently at version 4.5.1 across seven released versions, is a tray-resident local proxy in the developer tools and AI infrastructure category that manages OAuth2 flows and access control for APIs and MCP servers. It addresses two common problems: MCP servers are increasingly locked behind OAuth2 while most MCP clients expect a bare HTTP endpoint with no authentication, and an agent connected to multiple servers normally sees every available tool with no way to restrict it to a specific subset. RavensPort solves both by running a local reverse proxy on 127.0.0.1, holding the OAuth2 grants and API keys for upstream services, and composing those upstreams into filtered, per-agent MCP endpoints, so pointing an agent at http://127.0.0.1:5559/mcp/ exposes exactly the granted toolset drawn from as many upstreams as needed, including ones the agent could never reach on its own. Its routes feature attaches a live OAuth2 token or a static API key to every forwarded request, keeping clients free of authentication handling, and credentials can be placed wherever the upstream expects them—an Authorization header, any other header, a query parameter, or a request-body field—with a custom value prefix; a route may attach none, one, or several credentials at once, the same credential may appear in more than one place, and tokens refresh automatically ten minutes before expiry. Its funnels feature pools several MCP servers behind a single local endpoint and selects exactly which tools, resources, and prompts it exposes, giving each agent its own funnel so tightening one agent's reach never affects another, with a key available per endpoint.
Tags: